fix(proxy): retire cooldown-suppressed HTTP bridge sessions - #49
Merged
Conversation
Prevent hard-key retry-circuit cooldown paths from leaving newly opened, unsubmitted bridge sessions reusable. Preserve authorized replay bypasses and the existing cooldown response envelope. Fixes Soju06#1943 Source sidechat: 01a04718-7322-72d0-b4b3-8f5bb4581157 Recovered from: 2268f8c (cherry picked from commit 2a1ce99)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fable5 analysis
Fable5 (claude-fable-5, response
msg_l4vLQ0i8RzQiFjCGE2W7cOiE) evaluated the issue and found Strategy A (mark the session for retirement and use the existing bounded drain-retirement path after cooldown suppression) feasible with minimal risk. Strategy B would require broader request-admission plumbing and was not selected.Validation
sqlite3.OperationalError: no such table: file_account_pins)make architecture-check: passedmake typecheck: passedFixes Soju06#1943
Upstream issue: Soju06#1943
Source sidechat: 01a04718-7322-72d0-b4b3-8f5bb4581157
Recovered from: 2268f8c